docs(lstk hotfix): update CLI reference to v0.23.0 - #912
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying localstack-docs with
|
| Latest commit: |
64c9d0d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bc4895ee.localstack-docs.pages.dev |
| Branch Preview URL: | https://claude-hopeful-babbage-21z8t.localstack-docs.pages.dev |
|
The one red check here is Validate Refs, which is the repo's branch-naming gate ( This is unrelated to the docs changes themselves — Cloudflare Pages built the site successfully and the preview renders. The same check is red on the sibling in-flight I can't rename the branch to satisfy the gate from here (the branch name is fixed for this change). A maintainer can either merge via the usual docs flow that bypasses this check, or re-target/rename onto an Generated by Claude Code |
…acement Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…nto claude/hopeful-babbage-21z8t2 # Conflicts: # src/content/docs/aws/developer-tools/running-localstack/lstk/cloud-and-iac-commands.md
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Update: expanded scope to the Azure page + folded in the superseded PRsSince the last round, this PR now also brings Applied to both the AWS multi-page reference and the Azure page:
Snowflake: there's no Review threads: all three resolved — the CI: Cloudflare Pages builds green on the current head; the only red is the Cc @localstack/devx for visibility and any corrections. Generated by Claude Code |
mmaureenliu
left a comment
There was a problem hiding this comment.
Looks good in general. Minor fixes required. I assume tech details are correct after @anisaoshafi has done the eng review.
| `lstk setup aws` works non-interactively — it writes the profile with defaults and needs `--force` only to overwrite a conflicting `localstack` profile. | ||
| ::: | ||
|
|
||
| ## Targeting an external emulator |
There was a problem hiding this comment.
I think this belongs to the "Cloud and IaC Commands" section as this option is quite important for local dev use case. @peter-smith-phd what do you think?
There was a problem hiding this comment.
It lives in the global-options table because --endpoint-url is a persistent/global flag that applies across many commands (aws, az, the IaC tools, status, reset, snapshot), not just the IaC ones — and the full "Targeting an external emulator" section is right below it. I've also cross-referenced it from the Cloud & IaC page's intro note so it's discoverable from there. Happy to move the detailed section into Cloud & IaC (or duplicate a short callout there) if you and @peter-smith-phd prefer that placement — leaving this open for your call rather than restructuring unilaterally.
Generated by Claude Code
There was a problem hiding this comment.
@quetzalliwrites should this one share the same components as the aws lstk docs?
There was a problem hiding this comment.
Context for this one: there are no shared lstk components today — the AWS multi-page reference and this Azure single page each carry their own copy of the content (they're near-identical because lstk is one CLI). The Azure restructure #909 (by @quetzalliwrites) splits this single page into the same multi-page layout as AWS. My edits here are just keeping the live single page accurate for v0.22.2 in the meantime; if #909 lands first, these same corrections should be carried into it. Whether to factor the shared content into real shared components is a good call for that restructure — deferring to you and @quetzalliwrites.
Generated by Claude Code
|
@peter-smith-phd do you think it makes sense to apply your update to the first FAQ answer directly in this PR? |
…imental) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
hotfix): update CLI reference to v0.22.2hotfix): update CLI reference to v0.23.0
Update: extended to v0.23.0
The only user-facing delta since v0.22.2 is structured
The rest of v0.22.2 → v0.23.0 is deps bumps, a dev sandbox script, an internal PTY-input fix, and the internal The two open review threads (the Cc @localstack/devx for visibility and any corrections. Generated by Claude Code |
Motivation
The
lstkCLI reference reflected roughly v0.20.x, while the latest release is v0.23.0. This catches up the full v0.21.0 → v0.23.0 backlog — fixing claims that no longer match the CLI and documenting features that shipped in that range — and folds in the corrections from the three superseded doc-sync PRs (#833, #850, #877) that were closed when the docs were restructured.Reference surfaces in scope
There are no shared
lstkcomponents, so content lives directly in the pages.src/content/docs/aws/developer-tools/running-localstack/lstk/:index.mdx,authentication.md,configuration.mdx,cloud-and-iac-commands.md,snapshots.md,automation.mdx,lifecycle-commands.md,faq-and-troubleshooting.md,setup-and-maintenance.md.src/content/docs/azure/developer-tools/lstk.mdx(the single-page reference), brought to the same accuracy.What changed
v0.21.0 → v0.22.2
Corrections (stale / no longer accurate):
LOCALSTACK_AUTH_TOKENtakes precedence over a keyring token (v0.21+); the docs said the opposite and told users tolstk logoutfirst. Fixed on both pages (resolution list, admonition, env-var table).443is dropped with a warning (HTTPS stays on4566); only an explicitly-listed port is a hard requirement. Rewrote it (and fixed the Azure page's example, which usedtype = "aws").Additions (previously undocumented):
--endpoint-url/LSTK_ENDPOINT_URL— new "Targeting an external emulator" section, plus global-options and env-var rows and cross-references.snapshot versionssubcommand andpod:<name>:<version>refs onload/show.lstk aws --accountleading flag, with a "Selecting the account" section.container_nameandexpose_portsconfig fields.DOCKER_HOST→DOCKER_CONTEXT/CLI context → Linux socket → probe → SDK default), and the tailored start-command hint.lstk azconsuming its own flags;lstk awscompletion note.v0.23.0 delta
--jsonis now supported bystartandstatus(previously onlystop/reset/update). Updated the global-options table and the "Structured output" section on both pages, and added per-command--jsonnotes tostart(flatdataobject) andstatus(data.emulators[], plus the--no-resourcestoggle and--json --endpoint-urltargeting). AWS-only resource details are labeled as such on the shared Azure page.Snowflake
There is no
lstkreference page undersrc/content/docs/snowflake/onmainyet — it is being introduced by #910. There is nothing to correct there; these same fixes should be folded into #910 (and into the Azure restructure #909) since both are copies of this shared content.Needs a human decision
The Azure (#909) and Snowflake (#910)
lstkdoc restructures split this same content into the multi-page layout. Whichever of these merges first, the other must carry these corrections forward. The Azure edits here overlap #909 — coordinate on merge order.Review
Recommended: mostly additive reference content verified against the
v0.23.0CLI surface, but the auth-token precedence reversal and the Port 443 drop-with-warning reframing are user-facing behavior corrections worth a second look.Closes DOC-433
Cc @localstack/devx for visibility and any corrections.